migration to new isp - now private addresses showing up publicly?

[Matus UHLAR - fantomas]

On 23.05.23 12:22, Kaya Saman wrote:
>I've got a very strange problem that has emerged somehow after 
>migrating my isp.
>
>
>My setup previously used 2x servers in master/slave configuration for 
>my public "view" and then had 3x servers for the "internal" view. This 
>was working fine for years and I have been regularly testing using 
>online dns healthcheck sites such as mxtoolbox etc...
>
>
>Now when I try to run any type of check from mxtoolbox or other site 
>eg. https://dnschecker.org/ I am getting my private IP's showing 
>instead of the public ones?
>
>
>Initially it started off by my external zone files not transferring 
>which I managed to see that the information was trying to traverse my 
>NAT (I know, not the best practice to have all dns servers on the same 
>network).
>
>
>As a result external emails from my mail server are not working too 
>well with a hit and miss type thing going on right now.
>
>
>Just to go over, my zone files are fine as the 'external' ones only 
>have public ip addresses in them and do not include any type of 
>internal addressing whatsoever.
>
>
>Here's an example of the config in named.conf for the master:

>view "external" {
>    match-clients { !internals; any; };
[...]
>view "external" {
>    match-clients { !internals; any; };

I don't see your definition of "internals".
Also, I don't see your definition of internal view.
if internal IP addresses are visible on the internet, obviously the internet 
sources fall into your internal view, not into this one.


-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Silvester Stallone: Father of the RISC concept.