strange reply dumped URGENT

Herman Brule contact at herman-brule.com
Sat Jul 13 02:44:38 UTC 2024


Thanks, I'm looking how solve this, cleanly.

In my country only 1 ISP have IPv6, then I need keep IPv4.

I have 1 IPv4 for 1000 VPS, no way here to have more IPv4.

Then:

1) I'm not sure if my DNS authoritative on IPv6 reply correctly (but 
reply correctly to all my dig query)

2) I have to provide a way to my customer can resolve query on their DNS 
server on their IPv6 VPS, their need be able to just put their vps dns 
or at least common server dns (where I had to put their zone, then I 
dislike this idea)

For now your method fail, include I try:

zone "ore.org.bo" {
     type master;
     file "/etc/bind/ore.org.bo.db";
};

But failed too.

alpha_one_x86/BRULE Herman<alpha_one_x86 at first-world.info>
Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server management
IT, OS, technologies, research & development, security and business department

On 7/12/24 19:01, Mark Andrews wrote:
>
>> On 13 Jul 2024, at 04:38, Herman Brule via bind-users<bind-users at lists.isc.org>  wrote:
>>
>> Because the customer are into IPv6 zone
> Well all zones should be served by both IPv4 servers and IPv6 servers.  IPv6 is nearly 30 years old now.  There are
> sites that are IPv6 only because they would prefer to not have to run everything through 2 or 3 layers of NAT when
> they don’t need it at all for IPv6 and would really like to not have to send all there DNS queries though NAT64 boxes.
>
>> And the EDGE router connecting IPv4 and IPv6 is internal to the data center company, not accessible for the customer.
>> Forward zone to edge will be more complex, it's more simple just forward the query.
>> Thanks for you observation, but I know, I doing this quickly, I will keep like this for now, this will produce only problem for availability if the server is down.
> Except you are wrong.  You are writing here because it *is* causing you and everyone else a problem.  The correct way to
> fix this is to transfer the zone contents to the listed primary servers if you are using nameservers.  Alternatively
> don’t run nameservers at all but use IP level proxies. Either the whole address or port forward 53/TCP and 53/UDP.
>
>> alpha_one_x86/BRULE Herman<alpha_one_x86 at first-world.info>
>> Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server management
>> IT, OS, technologies, research & development, security and business department
>> On 7/12/24 14:28, Marco Moock wrote:
>>> Am 12.07.2024 um 14:13:03 Uhr schrieb Herman Brule via bind-users:
>>>
>>>
>>>> bind to my proxy from IPv4 to IPv6 zone
>>>>
>>> Why don't you simply run multiple authoritative servers, some only
>>> accessible by IPv6, some dual-stack?
>>>
>>> They are independent of each other and only the zone transfer need to
>>> work.
>>>
>>> I also see some strange things:
>>>
>>> m at ryz:~$ host 811.vps.confiared.com.
>>> 811.vps.CONFIARED.com has address 45.225.75.8
>>> 811.vps.CONFIARED.com has IPv6 address 2803:1920::c:1963
>>> m at ryz:~$ host 811b.vps.confiared.com.
>>> 811b.vps.CONFIARED.com is an alias for 811.vps.confiared.com.
>>> 811.vps.CONFIARED.com has address 45.225.75.8
>>> 811.vps.CONFIARED.com has IPv6 address 2803:1920::c:1963
>>> m at ryz:~$
>>>
>>> You should have redundant servers and not 2 NS records that point to
>>> the same machine.
>>>
>>> Please fix that first and update your glue records.
>>>
>>>
>> -- 
>> Visithttps://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 athttps://www.isc.org/contact/  for more information.
>>
>>
>> bind-users mailing list
>> bind-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/bind-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20240712/d11f92d8/attachment.htm>
-------------- next part --------------
$TTL 60
@       IN SOA 811.vps.confiared.com 811b.vps.confiared.com. confiared.com. (2020102000 86400 3600 3600000 300)
   3600 IN NS     811.vps.confiared.com.
   3600 IN MX     1 smtp.testadmin.ovh.
   3600 IN A     45.225.75.8
   3600 IN AAAA    2803:1920::c:1963
a        IN A     45.225.75.8
aaaa        IN AAAA     2803:1920::c:1963
smtp        IN CNAME     ore.org.bo.
www        IN CNAME     ore.org.bo.
*          IN CNAME     ore.org.bo.


More information about the bind-users mailing list