Heal Your Church WebSite


Teaching, rebuking, correcting & training in righteous web design.

Wanted : someone who’s got some dedicated server experience

Either my registrar has botched the domain I’m going to use for a hostname, or I’ve totally messed-up WHM.

If you’ve set up a dedicated server before, then leave a comment. I’ve got some questions.

Here’s what I get when I enter the following command … though the names and IP addresses have been mangled to protect the site:

# nslookup 123.45.67.890

Server: 123.45.67.890
Address: 123.45.67.890#53

Non-authoritative answer:
170.179.79.66.in-addr.arpa name = NS1.BOGUSNAME.US.

Authoritative answers can be found from:
179.79.66.in-addr.arpa nameserver = ns1.mangled.com.
179.79.66.in-addr.arpa nameserver = ns2.mangled.com.
ns1.mangled.com internet address = 66.55.444.1
ns2.mangled.com internet address = 66.55.444.2

Yes, I did register my nameservers with my registar.
Yes, I did ask my hosting company to establish a reverse DNS for my namesevers.
Still no joy.

If the above sounds like old hat to you, then leave a comment.

2 Comments

  1. Your example was difficult to follow since you changed some of the data. However, the following should be true: When you do an nslookup of a domain, let’s say, example.com, you might get an IP address of n.n.n.n where n is a number between 0 and 255 inclusive with some exclusions for broadcast addresses, etc.

    Then when you do a reverse lookup of n.n.n.n you should get “example.com” in our example above. The in-addr.arpa is basically the IP address backwards and has to do how the reverse lookups are performed for maximum efficiency. Now there are all sorts of things that can make life more interesting such as alias addresses (“CNAME” records), “MX” records (for email), and the ability of many domain registrars to “forward” your domain to any server you choose. Changes to any of the above may take anywhere from a few minutes to several days to propagate out to all requesting servers, but that’s another whole can of worms. So the bottom line is that is if your forward address (example.com in my example) resolves to an IP that points to your server and the PTR record (reverse address–AKA in-addr.arpa) points back to your domain, you should be ok. If they don’t, you need to find out whether your “A” record (Address record) is incorrect, or your “PTR” record (reverse lookup) is incorrect, both of whom are controlled by the server you’ve made responsible for your domain.

    Obviously it’s the “A” (Address) record that will get people to your site, and the one that must be absolutely correct for things to work properly. The PTR (reverse) record should be correct, but won’t necessarily be fatal if it is missing or correct, though in the long run that’s not a good thing.

    So my question to you is when you do a nslookup of your domain, do you get the correct IP address of your server? If not, then your DNS “A” record may be incorrect or missing from the DNS server who has the autority over your domain.

  2. John is right. Not only are his remarks on DNS entries correct, but your mangled examples are tough to follow. If you need help and can share more info, I’ll do what I can to help. I run my own server and have a bit of experience with domains and DNS.