Forum Moderators: phranque

Message Too Old, No Replies

Changing nameservers - I'm stuck!

Server not listening on port 53?

         

FaceLikeBambi

11:48 am on Nov 24, 2005 (gmt 0)

10+ Year Member



Hiya,

Any advice on this situation would be very, very appreciated! ;) This topic isn't about domain name values or registration, so I though this would be best place for it...

1) I want to change the nameservers for my domain earlex.fr to:

<snip>

2) My registrar won't change it because this test is failing:

<snip>

It reports that the server doesn't listen/answer on port 53 for TCP.

The registrars tell me this:

The IP address for the .fr registry is as follows: <snip>

and my hosts need to open port 53 for this IP address.

3) My hosts say that "it is impossible to open a port for a /24". They need a specific IP address.

4) The registrars say this is the only address info they can provide. There is nothing else.

I'm stuck!

Thanks,
Jason

[edited by: physics at 4:43 am (utc) on Nov. 25, 2005]
[edit reason] No specific domains or IPs please, see TOS. [/edit]

Romeo

1:23 pm on Nov 24, 2005 (gmt 0)

10+ Year Member



Hi Jason,

as you specified your domain and nameservers (which is against the TOS of this forum, by the way), I just checked and found your nameserver authoritatively responding to my arbitrary SOA request.

Most likely my request was a common UDP request (I can't check this, as I can't send port probes from here).
However, the registrar's test said your nameservers don't answer on *TCP*.
A nameserver should reply both on 53/UDP as well as on 53/TCP requests.

This could be a local nameserver configuration issue on your servers, or a port forwarding issue on your provider's side.

The IP address of the registrar does not matter in this case. An authoritative nameserver has to accept queries for its domains from *everywhere* in the internet /32 -- otherwise the DNS concept would not work and your domains would be unreachable from large parts of the internet.

Regards,
R.