I go with my own nameservers for about a week, but i have a problem:

Domains which I set up within last week are not accessible by my browser at home or at work, but dnsstaff, dnsreport and network-tools... all of them said everything is all right. It's pingable and everything...

When I go with some public proxy, it's all OK! :shock:

Why is that? Is there any workaround?

Thanks.

Are your home and work machines connected via different ISP's or the same?

We are on same ISP, Jeff. Perhaps it's up to ISP, but then no one from my country using that ISP will not have acces to my server (or any SM server using their own DNS), and that's not good, i think...

If that's the case, then it really depends upon how your ISP has their DNS servers setup. I'd drop them a line - if other people can resolve the domains, that your DNS server seems to be working properly.

Thanks, bsykes.
But, in that case a good portion of the net is not accessible at one time thru my ISP because of their DNS not updating regularly?
That's somewhat...... bad.

I'm not sure I follow you. If you can't get to a large portion of the Internet, that is indeed bad, and you should probably check with your ISP.

Sorry, Ben.
i can access everything except my sites. I'm just saying i probably can't acces some others not propagated sites like mine in this case...

Best thing is to connect to your ISP - keep it simple but with necessary details.

Also use netstat to find the dns servers and their IP's that your local connection is using (sometimes this isn't common sense.) Then use dig and nslookup commands to query those (primary and seondary) dns servers directly to see what results they return. If unsure how to use these commands use --help or on linux man dig for example.

Weird issues like this are not that common, but they do happen. A while back I had to wait three weeks for one ISP to update their dns servers after moving a site, even though all values for this domain at my nameservers were set very low to facilitate the transfer and the rest of the world was viewing the new server. About three years ago, my ISP had a problem between their primary and secondary DNS server which lasted about three weeks until they fixed it which was very frustrating because one updated and one didn't so half the time you would get it and half the time not. These types of irritating but strange problems do happen from time to time.

About all you can do is to verify with the netstat/dig/nslookup commands that your ISP's dns servers are not returning the correct result even after waiting a reasonable amount of time for an update and then contact them and see if they will fix it for you.

Dig and netstat is ok, i think, but:

"nslookup - myISP.com"

I understood that this command is entering an interactive mode thru my ISP's nameservers, correct?

Anyway, when i do it, one of my domains is OK, and one is not. Exactly like in my browser.

No problem to wait a bit more, but will this happen always or this is just because my DNS server is a new guy on the net?