In our firewall we see that our new DHCP server without other applicaties sends outgoing traffic on port 53 to different DNS servers. Ofcourse our domain controllers are part of it itoo, so communicating with those servers is fine.
But i don't understand how a local DHCP server connects to this servers on port 53 while it's not in cloud or at a decentral location. Is this a setting?
The connections are too a DNS routering on the internet. And these domain all have connection with each other when i look at 'who is'.
| 15.211.192.12 | HOU3NS.HOUSTON.HP.COM |
| 15.211.192.12 | HOU3NS.HOUSTON.HP.COM |
| 15.219.145.12 | VANNS1.AMERICAS.HP.NET |
| 15.219.145.12 | VANNS1.AMERICAS.HP.NET |
| 37.48.122.225 | DNS3.INOVAMEDIA.NL |
| 37.97.255.53 | NS2.TRANSIP.NET |
| 37.97.255.53 | NS2.TRANSIP.NET |
| 46.101.153.24 | NS2.NETWORKING4ALL.NET |
| 46.101.153.24 | NS2.NETWORKING4ALL.NET |
| 52.2.199.197 | NS1.PARKINGCREW.NET |
| 52.22.2.242 | NS2.PARKINGCREW.NET |
| 52.64.97.236 | NS1.PARKINGCREW.NET |
| 52.64.133.131 | NS2.PARKINGCREW.NET |
| 52.68.87.177 | NS1.PARKINGCREW.NET |
| 52.69.248.231 | NS2.PARKINGCREW.NET |
| 52.76.100.92 | EC2-52-76-100-92.AP-SOUTHEAST-1.COMPUTE.AMAZONAWS.COM |
| 52.76.100.92 | EC2-52-76-100-92.AP-SOUTHEAST-1.COMPUTE.AMAZONAWS.COM |
| 52.88.191.171 | NS1.PARKINGCREW.NET |
| 52.89.204.2 | NS2.PARKINGCREW.NET |
| 54.75.227.14 | NS1.PARKINGCREW.NET |
| 54.75.226.194 | NS2.PARKINGCREW.NET |
| 57.67.40.20 | NS1.EXT.PHILIPS.COM |
| 57.67.40.20 | NS1.EXT.PHILIPS.COM |
| 57.73.36.68 | NS3.EXT.PHILIPS.COM |
| 57.73.36.68 | NS3.EXT.PHILIPS.COM |
| 57.77.21.76 | NS2.EXT.PHILIPS.COM |
| 57.77.21.76 | NS2.EXT.PHILIPS.COM |
| 62.212.64.121 | NS1.LEASEWEB.NL |
| 62.212.78.199 | NS4.LEASEWEB.NET |
Can anybody explain this behaviour and how to solve this.
Kind regards,
André