Hellos,

i am lazy, therefore use dnsstuff.com. One may say whatever about it...

...but it reports

ERROR: Your nameservers report glue that is different from what the parent servers report. This will cause DNS servers to get confused; some may go to the IP provided by the parent servers, while others may get to the ones provided by your authoritative DNS servers. Problem record(s) are:

ns2.journeyman.co.uk.: Parent server (ns6.nic.uk) says A record is 209.124.81.27, but authoritative DNS server (209.124.81.26) says it is 209.124.81.26 ns2.journeyman.co.uk.: Parent server (ns6.nic.uk) says A record is 209.124.81.27, but authoritative DNS server (209.124.81.27) says it is 209.124.81.26

Seems to be a problem on their dns setup - right?

stef

On 24/09/2010 21:12, Juerg Reimann wrote:

What the heck is going on? Any DNS guru out there?

Thanks, Juerg

I get the same results as you:

From CH: # dig +trace www.journeyman.co.uk SOA +short ;; connection timed out; no servers could be reached

From UK: # dig +trace www.journeyman.co.uk SOA +short CNAME journeyman.co.uk. from server ns2.journeyman.co.uk in 131 ms. SOA ns1.journeyman.co.uk. phil.qawebhosting.com. 2010051402 86400 7200 3600000 86400 from server ns2.journeyman.co.uk in 131 ms.

Could be misconfigured views at the (looks like) single name server: ns1.journeyman.co.uk. 13470 IN A 209.124.81.26 ns2.journeyman.co.uk. 13459 IN A 209.124.81.26

Maybe "phil at qawebhosting.com" knows more if you havent spoken to him already.

Andy.

Hi,

They only have two DNS servers in the same subnet, and the subnet is unreachable from here. It works where it's still cached in the DNS.

# whois journeyman.co.uk

Domain name: journeyman.co.uk

Name servers: ns1.journeyman.co.uk 209.124.81.26 ns2.journeyman.co.uk 209.124.81.27

# dig @209.124.81.26 www. journeyman.co.uk

times out

# traceroute -n 209.124.81.26 traceroute to 209.124.81.26 (209.124.81.26), 64 hops max, 40 byte packets 1 82.195.224.1 9.256 ms 0.461 ms 0.228 ms 2 208.50.86.177 18.833 ms 134.398 ms 4.842 ms 3 67.17.105.218 110.320 ms 110.295 ms 110.122 ms 4 207.218.80.218 111.523 ms 111.428 ms 111.390 ms 5 64.94.0.83 190.231 ms 64.94.0.19 208.240 ms 64.94.0.83 207.369 ms 6 64.94.3.122 111.035 ms 110.894 ms 111.033 ms 7 69.61.56.38 110.936 ms 110.787 ms 110.883 ms 8 69.61.22.178 111.167 ms 111.304 ms 111.178 ms 9 * * * 10 * * *

NetRange: 209.124.64.0 - 209.124.95.255 CIDR: 209.124.64.0/19 OriginAS: NetName: DRAGON-BLK-1 NetHandle: NET-209-124-64-0-1 Parent: NET-209-0-0-0-0 NetType: Direct Allocation NameServer: NS1.DRAGON.COM NameServer: NS2.DRAGON.COM Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE

Interesting comment ...

-- Martin

I have a tricky one. For quite a while I've been unable to resolve www.journeyman.co.uk. I talked to these guys and they were quite unaware of any problem and even insisted that they have no problems at all. I can't resolve the name on either Cablecom, Bluewin, Swisscom Mobile, Nine, and so on. I almost gave up, but now I see that everything is fine when I'm connected to a host in the US over VPN.