Net::DNS::Update when Something Goes Wrong

2014-09-18 Thread Martin G. McCormick
This is a perl module but my question is pure bind. Is
anyone familiar enough with this perl module to say whether the
packets are sent as TCP or udp? If udp, one would think that if
a packet was sent to do a job and the DNS failed to receive it
the world would look the same to the sender as it would if the
DNS got the packet and the job went through without a problem.

I have been using this module in some scripts and it
normally works perfectly but on occasion, we have had things
happen such as trying to replace old forward lookups with new
ones using the same IP address but a different A record name.
The old ones hung around along with the new ones to form
redundant A records and nobody was the wiser at the time.
If there is that ambiguity, the fix would be to do
lookups just after the job to verify that everything went as
expected.
Thanks.

Martin McCormick
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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


Re: Net::DNS::Update when Something Goes Wrong

2014-09-18 Thread Kevin Darcy

On 9/18/2014 12:33 PM, Martin G. McCormick wrote:

This is a perl module but my question is pure bind. Is
anyone familiar enough with this perl module to say whether the
packets are sent as TCP or udp? If udp, one would think that if
a packet was sent to do a job and the DNS failed to receive it
the world would look the same to the sender as it would if the
DNS got the packet and the job went through without a problem.

I have been using this module in some scripts and it
normally works perfectly but on occasion, we have had things
happen such as trying to replace old forward lookups with new
ones using the same IP address but a different A record name.
The old ones hung around along with the new ones to form
redundant A records and nobody was the wiser at the time.
If there is that ambiguity, the fix would be to do
lookups just after the job to verify that everything went as
expected.

and/or use prereqs.

- Kevin
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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


Re: Net::DNS::Update when Something Goes Wrong

2014-09-18 Thread Martin G. McCormick
Kevin Darcy writes:
 and/or use prereqs.
Of course! Thank you. I was so honed in on something
more complicated that prereqs didn't cross my mind. I should be
able to put a strategy together that we can trust using those.

Martin
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

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