Re: Bind to Bind DNS Lookup - Returns wildcard value for defined A record

[Ondřej Surý]

Also:- make the record self-contained, don’t make us go elsewhere, especially not to a place where data could disappear at the whim of the owner (as seen recently)- and finally, describe what you see, don’t speculate what it might be; by describing you are less likely to miss an important detailOndřej--Ondřej Surý — ISC (He/Him)My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.On 16. 7. 2023, at 10:25, Greg Choules via bind-users  wrote:Real data please:- example queries (genuine, not invented for illustration)- real domains- real IP addresses- packet captures- both BIND server configs- zone file contents- startup logsThere are so many things it *could* be, the more information the better.Cheers, GregOn Sun, 16 Jul 2023 at 09:09, OwN-3m-All  wrote:I've got a bind recursion DNS server setup that is returning the wrong value for an outside domain that I also maintain and host on another server running a bind DNS server.  Yet Google's DNS and other major DNS providers respond with the correct IP address A record when querying.  I can't figure out why my recursion enabled instance is not returning the correct IP address for a specific host.  Rather, it returns the wildcard value from the zonefile rather than the specifically specified A record entry created for that host.  It appears bind to bind is returning the wildcard value for a specifically defined host in the zonefile from the server it's hosted on.Is this a recent bug in bind?  More information about my setup and issue can be found here:https://serverfault.com/questions/1136914/bind-recursion-dns-server-returning-wildcard-address-for-host-despite-exact-entrFrom what I found online, if there's a specific host A record entry defined, it should always return that IP.  Wildcard is only for those not defined.  Yet, when I remove the wildcard from the zonefile, my bind recursion instance returns the correct value, but not when the wildcard entry is there.  But Google and other major DNS providers return the non-wildcard value as expected.Any help is appreciated.
-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this listISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.bind-users mailing listbind-users@lists.isc.orghttps://lists.isc.org/mailman/listinfo/bind-users-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Re: Bind to Bind DNS Lookup - Returns wildcard value for defined A record

[Greg Choules via bind-users]

Real data please:
- example queries (genuine, not invented for illustration)
- real domains
- real IP addresses
- packet captures
- both BIND server configs
- zone file contents
- startup logs

There are so many things it *could* be, the more information the better.

Cheers, Greg

On Sun, 16 Jul 2023 at 09:09, OwN-3m-All  wrote:

> I've got a bind recursion DNS server setup that is returning the wrong
> value for an outside domain that I also maintain and host on another server
> running a bind DNS server.  Yet Google's DNS and other major DNS providers
> respond with the correct IP address A record when querying.  I can't figure
> out why my recursion enabled instance is not returning the correct IP
> address for a specific host.  Rather, it returns the wildcard value from
> the zonefile rather than the specifically specified A record entry created
> for that host.
>
> It appears bind to bind is returning the wildcard value for a specifically
> defined host in the zonefile from the server it's hosted on.
>
> Is this a recent bug in bind?  More information about my setup and issue
> can be found here:
>
>
> https://serverfault.com/questions/1136914/bind-recursion-dns-server-returning-wildcard-address-for-host-despite-exact-entr
>
> From what I found online, if there's a specific host A record entry
> defined, it should always return that IP.  Wildcard is only for those not
> defined.  Yet, when I remove the wildcard from the zonefile, my bind
> recursion instance returns the correct value, but not when the wildcard
> entry is there.  But Google and other major DNS providers return the
> non-wildcard value as expected.
>
> Any help is appreciated.
> --
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
> from this list
>
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
>
> bind-users mailing list
> bind-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Re: Bind to Bind DNS Lookup - Returns wildcard value for defined A record

[Matus UHLAR - fantomas]

On 16.07.23 02:08, OwN-3m-All wrote:

I've got a bind recursion DNS server setup that is returning the wrong
value for an outside domain that I also maintain and host on another server
running a bind DNS server.  Yet Google's DNS and other major DNS providers
respond with the correct IP address A record when querying.  I can't figure
out why my recursion enabled instance is not returning the correct IP
address for a specific host.  Rather, it returns the wildcard value from
the zonefile rather than the specifically specified A record entry created
for that host.

It appears bind to bind is returning the wildcard value for a specifically
defined host in the zonefile from the server it's hosted on.

Is this a recent bug in bind?  More information about my setup and issue
can be found here:

https://serverfault.com/questions/1136914/bind-recursion-dns-server-returning-wildcard-address-for-host-despite-exact-entr

From what I found online, if there's a specific host A record entry
defined, it should always return that IP.  Wildcard is only for those not
defined.  Yet, when I remove the wildcard from the zonefile, my bind
recursion instance returns the correct value, but not when the wildcard
entry is there.  But Google and other major DNS providers return the
non-wildcard value as expected.


Please provide concrete example, I can't query fun.test.test.me. nor 
test.test.me.

--
Matus UHLAR - fantomas, uh...@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.
Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Bind to Bind DNS Lookup - Returns wildcard value for defined A record

[OwN-3m-All]

I've got a bind recursion DNS server setup that is returning the wrong
value for an outside domain that I also maintain and host on another server
running a bind DNS server.  Yet Google's DNS and other major DNS providers
respond with the correct IP address A record when querying.  I can't figure
out why my recursion enabled instance is not returning the correct IP
address for a specific host.  Rather, it returns the wildcard value from
the zonefile rather than the specifically specified A record entry created
for that host.

It appears bind to bind is returning the wildcard value for a specifically
defined host in the zonefile from the server it's hosted on.

Is this a recent bug in bind?  More information about my setup and issue
can be found here:

https://serverfault.com/questions/1136914/bind-recursion-dns-server-returning-wildcard-address-for-host-despite-exact-entr

>From what I found online, if there's a specific host A record entry
defined, it should always return that IP.  Wildcard is only for those not
defined.  Yet, when I remove the wildcard from the zonefile, my bind
recursion instance returns the correct value, but not when the wildcard
entry is there.  But Google and other major DNS providers return the
non-wildcard value as expected.

Any help is appreciated.
-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users