m0rpheu5
Jun 23 2008, 06:23 AM
Iīm having a big problem with DNS on to Server on The Planet, i asked to support to resolve the problem, but i think that they doesnīt know how to do this.
The problem is about the domain totalprint.com.br, is not my client, only me and my client is trying to send email to this domain, i can send email from gmail, hotmail, yahoo and etc, but with my 2 Server i canīt, so I try to ping this domain from my servers and i donīt get a resolution, so i try to ping ths Ip, and i got the resolution, so i thought to ping from others server, i log in my Windows Server in the Same DC on The Planet, and ping the domain without problem, i log into my other 4 server into another Data Center, and i ping ok too, so the problem is with my DNS on this 2 server, or iīm mistake??
in 5 server i donīt have problems, i can send email, etc, and into other 2 server i canīt, where is the problem?
The Planet support told me that the problem is not on my server, so where is?
Please Help me, the problem is during more than one week.
Thanks
eth00
Jun 23 2008, 12:20 PM
Sounds like your /etc/resolv.conf is bad and it is related to your server.
ThePlanet lists nameservers somewhere that you can use but if nothing else try 4.2.2.1 and 4.2.2.2 and everything should start working right away - very simple fix.
Tomy Durden
Jun 23 2008, 01:02 PM
It looks like your domain is suffering from a circular dependency. I'm unable to resolve it from inside or outside of our network. It's recommended that you use name servers which are not defined by the same domain or use glue records.
A little plagerism from wikipedia:
QUOTE
Circular dependencies and glue records
Name servers in delegations appear listed by name, rather than by IP address. This means that a resolving name server must issue another DNS request to find out the IP address of the server to which it has been referred. Since this can introduce a circular dependency if the nameserver referred to is under the domain that it is authoritative of, it is occasionally necessary for the nameserver providing the delegation to also provide the IP address of the next nameserver. This record is called a glue record.
For example, assume that the sub-domain en.wikipedia.org contains further sub-domains (such as something.en.wikipedia.org) and that the authoritative name server for these lives at ns1.something.en.wikipedia.org. A computer trying to resolve something.en.wikipedia.org will thus first have to resolve ns1.something.en.wikipedia.org. Since ns1 is also under the something.en.wikipedia.org subdomain, resolving ns1.something.en.wikipedia.org requires resolving something.en.wikipedia.org which is exactly the circular dependency mentioned above. The dependency is broken by the glue record in the nameserver of en.wikipedia.org that provides the IP address of ns1.something.en.wikipedia.org directly to the requestor, enabling it to bootstrap the process by figuring out where ns1.something.en.wikipedia.org is located.
CODE
tdurden@PlanetShell ~ $ dig SOA totalprint.com.br +trace
; <<>> DiG 9.2.4 <<>> SOA totalprint.com.br +trace
;; global options: printcmd
. 232396 IN NS J.ROOT-SERVERS.NET.
. 232396 IN NS F.ROOT-SERVERS.NET.
. 232396 IN NS E.ROOT-SERVERS.NET.
. 232396 IN NS L.ROOT-SERVERS.NET.
. 232396 IN NS M.ROOT-SERVERS.NET.
. 232396 IN NS I.ROOT-SERVERS.NET.
. 232396 IN NS B.ROOT-SERVERS.NET.
. 232396 IN NS D.ROOT-SERVERS.NET.
. 232396 IN NS A.ROOT-SERVERS.NET.
. 232396 IN NS H.ROOT-SERVERS.NET.
. 232396 IN NS C.ROOT-SERVERS.NET.
. 232396 IN NS G.ROOT-SERVERS.NET.
. 232396 IN NS K.ROOT-SERVERS.NET.
;; Received 504 bytes from 216.234.234.30#53(216.234.234.30) in 1 ms
br. 172800 IN NS B.DNS.br.
br. 172800 IN NS C.DNS.br.
br. 172800 IN NS D.DNS.br.
br. 172800 IN NS E.DNS.br.
br. 172800 IN NS A.DNS.br.
;; Received 227 bytes from 192.58.128.30#53(J.ROOT-SERVERS.NET) in 40 ms
totalprint.com.br. 86400 IN NS ns1.totalprint.com.br.
totalprint.com.br. 86400 IN NS ns2.totalprint.com.br.
;; Received 103 bytes from 200.189.40.10#53(B.DNS.br) in 395 ms
dig: couldn't get address for 'ns1.totalprint.com.br': failure
m0rpheu5
Jun 23 2008, 01:22 PM
strange, in my office computer, and into my other server into Cari.net, i got this.
[root@l2 ~ ]# dig SOA totalprint.com.br +trace
; <<>> DiG 9.4.2 <<>> SOA totalprint.com.br +trace
;; global options: printcmd
. 85405 IN NS J.ROOT-SERVERS.NET.
. 85405 IN NS F.ROOT-SERVERS.NET.
. 85405 IN NS C.ROOT-SERVERS.NET.
. 85405 IN NS A.ROOT-SERVERS.NET.
. 85405 IN NS I.ROOT-SERVERS.NET.
. 85405 IN NS G.ROOT-SERVERS.NET.
. 85405 IN NS M.ROOT-SERVERS.NET.
. 85405 IN NS H.ROOT-SERVERS.NET.
. 85405 IN NS D.ROOT-SERVERS.NET.
. 85405 IN NS K.ROOT-SERVERS.NET.
. 85405 IN NS B.ROOT-SERVERS.NET.
. 85405 IN NS L.ROOT-SERVERS.NET.
. 85405 IN NS E.ROOT-SERVERS.NET.
;; Received 272 bytes from 127.0.0.1#53(127.0.0.1) in 22 ms
br. 172800 IN NS A.DNS.br.
br. 172800 IN NS B.DNS.br.
br. 172800 IN NS C.DNS.br.
br. 172800 IN NS D.DNS.br.
br. 172800 IN NS E.DNS.br.
;; Received 227 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 175 ms
totalprint.com.br. 86400 IN NS ns1.totalprint.com.br.
totalprint.com.br. 86400 IN NS ns2.totalprint.com.br.
;; Received 103 bytes from 200.189.40.10#53(B.DNS.br) in 360 ms
totalprint.com.br. 9600 IN SOA sauron.totalprint.com.br. root.sauron.totalprint.com.br. 2008011505 21600 1800 1555200 86400
totalprint.com.br. 9600 IN NS ns3.totalprint.com.br.
totalprint.com.br. 9600 IN NS ns2.totalprint.com.br.
totalprint.com.br. 9600 IN NS ns1.totalprint.com.br.
;; Received 185 bytes from 200.232.28.130#53(ns2.totalprint.com.br) in 198 ms
Donīt you think that the problem is on The Planetīs Network?
Tomy Durden
Jun 23 2008, 03:14 PM
It's probable that the records for nsx.totalprint.com.br are cached in your local recursive name servers which would result in a successful resolution. As long as there's a regular query for the record, it'll stay cached, but if it expires the recursive NS will no longer be able to get back to the authoritative name server for the domain.
m0rpheu5
Jun 24 2008, 10:20 AM
donīt you think that is strange to be a DNS cache in more than 20 different connections, i prefer to believe that the problem is only in 2 servers of The Planet, because my tird server is OK.