Re: strange reply dumped URGENT

Am Fri, 12 Jul 2024 22:44:38 -0400 schrieb Herman Brule : > For now your method fail, include I try: > > zone "ore.org.bo" { >     type master; >     file "/etc/bind/ore.org.bo.db"; > }; Only have one, exactly one master for a zone. Everything else will create a big mess. The other servers ar

Re: strange reply dumped URGENT

Am Fri, 12 Jul 2024 15:51:32 -0400 schrieb Herman Brule : > Loop detected! We were referred back to '45.225.75.8' That's why I say: Have real NS records that point to unique systems. If you forward, make sure the other machine is the master. I operate DNS with 2 NS records, one dual-stack,

Re: strange reply dumped URGENT

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 pro

Re: strange reply dumped URGENT

> On 13 Jul 2024, at 04:38, Herman Brule via bind-users > 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 r

Re: strange reply dumped URGENT

Named can NOT be configured as a proxy server for an authoritative server. It is NOT designed to be run like that. Forwarding is for RECURSIVE queries (made by stub resolvers) not ITERATIVE queries (made by recursive servers). When you specify forwarding you tell the recursive server to behav

Re: strange reply dumped URGENT

I see https://mxtoolbox.com/SuperTool.aspx?action=a%3aore.org.bo&run=toolpage Loop detected! We were referred back to '45.225.75.8' dns check mx lookup

Re: strange reply dumped URGENT

Am 12.07.2024 um 14:56:28 Uhr schrieb Herman Brule via bind-users: > The edge router receive the query, should just forward to the IP into > the named.conf.rproxy (then IPv6 master) So bind runs on this router? What is the hostname of this router? To which IP addresses does it point? -- Gruß

Re: strange reply dumped URGENT

The edge router receive the query, should just forward to the IP into the named.conf.rproxy (then IPv6 master) alpha_one_x86/BRULE Herman Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server management IT, OS, technologies, research & development, security and busines

Re: strange reply dumped URGENT

Am 12.07.2024 um 14:38:58 Uhr schrieb Herman Brule: > Because the customer are into IPv6 zone So the master DNS is IPv6 only? No problem for the zone transfer. > And the EDGE router connecting IPv4 and IPv6 is internal to the data > center company, not accessible for the customer. In which way

Re: strange reply dumped URGENT

Because the customer are into IPv6 zone 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 t

Re: strange reply dumped URGENT

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

strange reply dumped URGENT

Hi, I have dns problem, mostly show by dig A smtp.ore.org.bo @8.8.8.8 Then I have dump the connection by dumpcap, the raw reply by bind is wrong. As attached file: - dump of ethernet interface I have into /etc/bind/named.conf.rproxy: zone "ore.org.bo" {    type forward;    forward on

Re: Accepting TCP connection failed: socket is not connected

There’s no issue. The message is already logged at INFO level. Ondrej -- 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 12. 7. 2024, at 10:07, sami.ra...@sofrecom.com wrote: > >

RE: Accepting TCP connection failed: socket is not connected

Hello Do I need to update BIND to version 9.18 to fix this issue? https://gitlab.isc.org/isc-projects/bind9/-/issues/2700 Regards -Message d'origine- De : bind-users De la part de bind-users-requ...@lists.isc.org Envoyé : jeudi 11 juillet 2024 20:26 À : bind-users@lists.isc.org Objet :