Fix your DNS, the ".com" glue records don't match your NS records, this
can lead to problems with some DNS caching resolvers.
$ dig +noall +ans +auth +add -t ns e-surland.com @f.gtld-servers.net
e-surland.com. 172800 IN NS ns1.e-surland.com.
e-surland.com. 172800 IN NS ns2.e-surland.com.
ns1.e-surland.com. 172800 IN A 146.255.100.24
ns2.e-surland.com. 172800 IN A 213.27.204.236
$ dig +noall +ans +auth +add -t ns e-surland.com @ns1.e-surland.com
e-surland.com. 259200 IN NS ns1.e-surland.com.
ns1.e-surland.com. 259200 IN A 146.255.100.24
$ dig +noall +ans +auth +add -t ns e-surland.com @ns2.e-surland.com
dig: couldn't get address for 'ns2.e-surland.com': not found
Especially since one of the IPs in the glue records is a lame
delegation:
$ dig +noall +ans +auth +add -t ns e-surland.com @213.27.204.236 | sort
. 3600000 IN NS A.ROOT-SERVERS.NET.
. 3600000 IN NS B.ROOT-SERVERS.NET.
. 3600000 IN NS C.ROOT-SERVERS.NET.
. 3600000 IN NS D.ROOT-SERVERS.NET.
. 3600000 IN NS E.ROOT-SERVERS.NET.
. 3600000 IN NS F.ROOT-SERVERS.NET.
. 3600000 IN NS G.ROOT-SERVERS.NET.
. 3600000 IN NS H.ROOT-SERVERS.NET.
. 3600000 IN NS I.ROOT-SERVERS.NET.
. 3600000 IN NS J.ROOT-SERVERS.NET.
. 3600000 IN NS K.ROOT-SERVERS.NET.
. 3600000 IN NS L.ROOT-SERVERS.NET.
. 3600000 IN NS M.ROOT-SERVERS.NET.
--
Viktor.
