Something is blocking an inbound connect on port 53

[perazim2]

TelkomSA ADSL. Put a dns server on the LAN and configured the Netgear DGN2200 router to forward inbound connects from the WAN to the server's LAN address. Known good server with working dns - named. This server is used by another group of dns servers acting as secondaries to load zones for access by the public internet.

The problem is that these secondary servers are unable to complete a zone transfer. My dns server is unreachable. I am using the public ip address assigned by Telkom for this test.

So my question is: Does Telkom block inbound connects in the same manner as the global cellular operators do?

Thanks,

Perazim

 

[stricken]

telkom doesn't block any ports on ADSL. Perhaps firewall / zone on 53 box

 

[ranger]

TelkomSA ADSL. Put a dns server on the LAN and configured the Netgear DGN2200 router to forward inbound connects from the WAN to the server's LAN address. Known good server with working dns - named. This server is used by another group of dns servers acting as secondaries to load zones for access by the public internet.

The problem is that these secondary servers are unable to complete a zone transfer. My dns server is unreachable. I am using the public ip address assigned by Telkom for this test.

So my question is: Does Telkom block inbound connects in the same manner as the global cellular operators do?

Thanks,

Perazim

No, we don't.

/me tests:

[me@work ~]$ dig @105.226.139.36 ranger.dnsalias.com axfr

; <<>> DiG 9.8.3-P4 <<>> @105.226.139.36 ranger.dnsalias.com axfr
; (1 server found)
;; global options: +cmd
ranger.dnsalias.com. 86400 IN SOA ranger.dnsalias.com. root.ranger.dnsalias.com. 44 10800 900 604800 86400
ranger.dnsalias.com. 86400 IN NS media.ranger.dnsalias.com.
ranger.dnsalias.com. 86400 IN A 192.168.2.1
media.ranger.dnsalias.com. 86400 IN A 192.168.2.26
[...]


You are forwarding both TCP and UDP (large requests and transfers are over TCP)? If not, it will just
$ dig @105.226.139.36 ranger.dnsalias.com axfr

; <<>> DiG 9.8.3-P4 <<>> @105.226.139.36 ranger.dnsalias.com axfr
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

You have added an ACL allowing the secondary to transfer the zone in question? If not, you will get something like:
$ dig @105.226.139.36 ranger.dnsalias.com axfr

; <<>> DiG 9.8.3-P4 <<>> @105.226.139.36 ranger.dnsalias.com axfr
; (1 server found)
;; global options: +cmd
; Transfer failed.

If you don't come right, please send a mail to [email protected] with some details (e.g. username, domain) and PM me the ticket number you get back, or the email address you sent from.

 

[perazim2]

telkom doesn't block any ports on ADSL. Perhaps firewall / zone on 53 box

Resolved. The european provider of dns services had a problem pulling my zone data and their diagnostics incorrectly pointed at my end as the source of trouble. Fixed now.

I just learned that Telkom will not assign fixed/static IP addresses here. What kind of thinking is this?

Thanks,

Perazim

 

[Pada]

If you want static IP addresses, then you need to get a business account. I'm not sure if Telkom's business accounts give you static IP's, but I know that you get like 5 with MWEB business.

 

[Tim the Techxpert]

Glad it was resolved
I think that Telkom will provide static addresses on a business account so approach them and get what you need.

They are not the unfriendly people that some claim they are

Regards

Tim

 

[ranger]

If you want static IP addresses, then you need to get a business account. I'm not sure if Telkom's business accounts give you static IP's, but I know that you get like 5 with MWEB business.

Before our migration in February, it wasn't really feasible to provide static IP addresses. This was one of the (many) reasons motivating the migration.

Static IP addresses are on the roadmap for this year. Timelines have not been finalised yet though.