Should webhost manager change the resolv.conf file when I added my name servers (ns.xxx.com and ns2.xxx.com)

I noticed mine has not changed, should it have? :uhh:

{resolv.conf}
domain darkorb.net
search darkorb.net
nameserver 127.0.0.1
nameserver 216.10.17.96
nameserver 216.10.17.96
nameserver 216.10.17.98
nameserver 216.10.17.99

sitekeeper,

resolve.conf is the configuration file that tells your server how to change an internet name into an internet address (an IP address).

It has nothing to do with outside users or what DNS server your domain or your customer's domains are pointed to.

Your resolve.conf file looks fine.

Matthew

Although I have not used this on a server, I would tend to agree.

The resolv.conf is just for your box to look up names->ips.

<thinking>

Do you really need that many nameservers?

I have only 2. Guess it is the more, the better.

Originally posted by Asia
<thinking>

Do you really need that many nameservers?

I have only 2. Guess it is the more, the better.

None of the Ip's are mine, that's why I was asking. I am guessing it has to do with cpanel/WHM :confused:

Thanks for the replies!

The name servers listed are called recursive DNS servers, most likely provided by your ISP. Don't worry about them unless you are having problems resolving internet addresses.

The name servers are queried in a round-robin fashion, so having two or four is fine.

Ignore the rest of this message, as it is likely to confuse you.

But the domain is the domain that your machine resides in. hercules.yahoo.com resides in the yahoo.com domain.

Search refers to the order in which addresses are looked up. If you had a search infoseek.com, and performed a lookup on the name 'zion' the host revolver would attempt to resolve zion.infoseek.com.

Hope this helps

Matt

Originally posted by matthewfong
The name servers listed are called recursive DNS servers, most likely provided by your ISP. Don't worry about them unless you are having problems resolving internet addresses.

The name servers are queried in a round-robin fashion, so having two or four is fine.

Ignore the rest of this message, as it is likely to confuse you.

But the domain is the domain that your machine resides in. hercules.yahoo.com resides in the yahoo.com domain.

Search refers to the order in which addresses are looked up. If you had a search infoseek.com, and performed a lookup on the name 'zion' the host revolver would attempt to resolve zion.infoseek.com.

Hope this helps

Matt


I am on a new dedicated server, I was thinking my domain name should have been in the file. I will have to wait for Network Solutions to add my name servers to find out if everything working right. (could be awhile) The manual for Web Hosting Manager is :confused:

Thanks
Bob

Hello
Yes, your name servers need to be on that list is they are not on that physical server.

The reason for this is that when you set up an account with subdomains on cpanel and the user tries to use one of them cpanel looks for the dns wildcard on the name servers listed in resolv.conf
If your name servers are not listed there then cpanel will not find the wildcard and the end user will get an error message in their Cpanel.

This should only affect you if you have more than one server and the DNS is held independently on one or two of them.

Gordon

Wow, a thread from the past..LOL

Anyhow, I have been trying to track down some small but pesky problems...ndc: connect errors, not able to keep the A name for my server, cppop slow, ftp login slow. Server flies otherwise, but those logins took a bit longer than I cared for.... hehehe

Anyhow, I tried many different "fixes" etc.. from Cpanel.net, tweaks to ProFTP etc... and no luck.

Well, it turns out that it *was* the resolv.conf file!! Those default settings are the problem... got rid of those darkorb setting and edited my own in..and Bang, much better.

Now that I am on a roll..... what to tweak next.... hehehe

<edt... added a bit later> LOL, now I notice after going through all of that....vi and all editing the resolv.conf file etc... etc... I updated to the latest Cpanel version... Now right there is a little new wizard to walk ya through that process. LOL Just passing that tidbit along incase anybody else runs into this isssue.

Hello
That wizard is Ok except on most of our servers it pops up all the time even when the settings are correct!

Good luck.

Gordon

If I run my primary and secondary DNS on the CPanel server itself, do I need to list those 2 ip's also after 127.0.0.1?

I did some searches in google, and I found several documents that say 127.0.0.1 should not be in resolv.conf when using BIND :confused:

Originally posted by barleduc
If I run my primary and secondary DNS on the CPanel server itself, do I need to list those 2 ip's also after 127.0.0.1?


No as 127.0.0.1 points to the box already.
I have always had severl aservers with a central DNS so I have always had to have my promary listed in resolv.conf
so that the subdomain function works before DNS propagation,
so I dont know about the other point.

Incidentally cpanel does not like lots of zone files.
We got to 8000 on two linked cpanel servers in different locations and things started to go badly wrong.
We had to shift to a Mysql driven system that generates the zone files and updates them once an hour on dedicated boxes for that purpose.

Gordon