Help! Problems with our nameservers are keeping the public from reaching all or some of our websites.

The domain ( along with the subdomains was  associated with a nameserver running on the same server that is hosting the domain. The domain has not propogated  properly across the internet, within a 3day period. Basically some internet users can reach it and some cannot. We've been operating on this server for almost 5 days.

We tried pinging from from our work location, but couldn't find a DNS record. Howeve we could reach one of the submdomains (

We tried running a trace afterwards and the jobs subdomain didn't  return the trace. see below.

Tracing route to []
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms
  2    <1 ms    <1 ms    <1 ms
  3    <1 ms    <1 ms    <1 ms
  4    24 ms    22 ms    22 ms
  5    22 ms    23 ms    22 ms
  6    23 ms    22 ms    22 ms
  7    23 ms    23 ms    22 ms
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *

Here is the named entry for the domain:

; cPanel 10.9.0-RELEASE_7965
; Zone file for
$TTL 14400
@      86400    IN      SOA  
( 2007031806        ; serial, todays date+todays
                86400           ; refresh, seconds
                7200            ; retry, seconds
                3600000         ; expire, seconds
                86400 )         ; minimum, seconds 86400 IN NS 86400 IN NS IN A IN A IN MX 0

ftp IN A
ads 14400 IN A 14400 IN A
directory 14400 IN A 14400 IN A
inform 14400 IN A
www.inform 14400 IN A
jobs 14400 IN A 14400 IN A
members 14400 IN A
www.members 14400 IN A
news 14400 IN A 14400 IN A
photos 14400 IN A 14400 IN A
survey 14400 IN A
www.survey 14400 IN A
test 14400 IN A
www.test 14400 IN A
videos 14400 IN A
www.videos 14400 IN A
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

its work for me, i think you have a dns that not update correctly in the middle, i recommend talk with your ISP

root@sonysz:~# ping
PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=49 time=147 ms
64 bytes from ( icmp_seq=2 ttl=49 time=150
its not your problem your configuration is ok talk with the isp guys

and a dig

; <<>> DiG 9.3.2 <<>>
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64969
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;               IN      A

;; ANSWER SECTION:        14294   IN      A

;; AUTHORITY SECTION:        86294   IN      NS        86294   IN      NS

;; Query time: 8 msec
;; WHEN: Tue Mar 20 13:17:49 2007
;; MSG SIZE  rcvd: 103
can we see the castings ???? :)  
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Chris DentPowerShell DeveloperCommented:

For the Tracert provided. If there is a problem accessing that site you need to look to your internal routing configuration, all the addresses in the route are private.

You need to see what those internet users that can't reach it are getting as an IP for that name. Something like this will tell you (> are just prompts):

C:\> nslookup
> set type=ns

You can see the TTL remaining for any particular record within nslookup with:

> set debug

Your TTL is correctly setting to 4 hours for the records within your zone (as you have specified above). Propogation just refers to the expiry of the TTL values set on zones or records.

mykkalAuthor Commented:
It's not just my ISP. It is many ISPs. Once we moved over to the new servers we seemed to propagate fine. Everything was fine for a day or so and then magically everything seemed to start falling off the internet. However I can get to the site fine from my home ISP which is Comcast. But from work I can't get to the main domain or any of the sub domains except one. That sub-domain which does work is My developer in London cannot get to anything except through IP address. Another friend in LA can see some sub-domains but not all.

There are two other sub-domains and none of them resolve.

The name of the nameservers should be and I'm curious as to why I see and in the results posted by pablouruguay...

Anyways as Chris-Dent asked I did a NS lookup for and got nothing. I then did an NSlookup for and got something. It’s weird.

NS Lookup of

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to timed-out

NS Lookup of

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to timed-out

Chris DentPowerShell DeveloperCommented:

But Faith1 and 2 are in your Zone File: 86400 IN NS 86400 IN NS

If they're not right then you must update them!

Chris DentPowerShell DeveloperCommented:

In fact it looks like that's exactly why it's breaking.

See the results on here:

You have Name Servers set correctly on the Root Servers (so the glue is right) but your own NS records are wrong.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
chenge the serial of the nameservers ALL nameservers and restart named please..
Chris DentPowerShell DeveloperCommented:

The Serial has no bearing on this if the NS records are still wrong in the Primary Name Servers zone file.

The name servers quoted on the Root Servers ( state the Name Server for are Faith1 and Faith2.

mykkalAuthor Commented:

Thats a bunch man. That DNS-Report made a different.
Chris DentPowerShell DeveloperCommented:

You're welcome.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.