Dns Resolution On Servers

[MikeJ]

Is it a true statement that any DNS resolution that takes place on TCH servers queries the authoritive TCH nameservers via some caching nameserver that doesn't look at the root servers directly?

 

Just asking for purposes of my migration. It seems that as far as the TCH servers are concerned, once I setup a domain in WHM, the server considers TCH authoritive for that domain, regardless if TCH is authoritive as defined by the registrar for the domain.

 

From a PHP script I whipped together to query DNS, this appears to be the case. The queries are getting the info from localhost, and are showing TCH as the authoritive name servers for domains I have setup on TCH, but not changed the nameservers at the registrar yet.

 

I just want to confirm that my findings are correct so I understand where my mail (which fails to certain domains at the moment when I attempt to send it through TCH because the server can't find the correct DNS info, which is what started this investigation) is getting DNS from, as well as my web sites, while I'm still in the process of migrating. This will help me make sure my migration of my critical domains is smooth.

 

Thanks! Rock Sign

[TCH-Rick]

That is the way things work. We have some accounts that use external mail servers, for example, and we have to set up the server so that email will be sent to the external server rather than delivered locally.

 

That is also the reason that we have the warning not to use an email address based on the domain name you are using for your account here when you sign up. The way the system works, the account is set up and then an email is sent with the log in information. If the email address given uses the domain name that was just set up our servers will deliver all mail to the default (or main) account of that domain on our server and the client will not receive it on the account he has been using.