Re: My Reverse Look Up suddenly stopped working for most servers

Am 08.02.2017 um 17:26 schrieb Majid Chavoshi: My DNS was working find, but the reverse look up suddenly stopped working for most servers (it still works for a few servers, I'd say it still works for 20% of servers). Where can I look? What to restart? What should I do? Thanks you don't

Re: My Reverse Look Up suddenly stopped working for most servers

don't reply off-list on mailing-lists! Am 08.02.2017 um 17:37 schrieb Majid Chavoshi: Hey reindl, Thanks so much for your reply. How would I find out if I own it or not? Sorry, but I'm kind of new at this; thanks. if you would have told the nameserver and sample ip's everybody already could

RE: Enforce EDNS

+1 to Alan. While I work at an ivory tower and support Mark's mission, in practice I don't have operational time (nor is it necessarily the best use of my time) to maintain a per-ip bypass. 100% in support of enabling this by default as long as their as an option to disable. -Michael >

My Reverse Look Up suddenly stopped working for most servers

Ladys & Gents, My DNS was working find, but the reverse look up suddenly stopped working for most servers (it still works for a few servers, I'd say it still works for 20% of servers). Where can I look? What to restart? What should I do? Thanks. -- *​* *Thank you & have a very nice day,*

RE: Clean up dynamic names

Kevin, I understand. Let me refocus the question. DHCP: I know DHCP will remove the info when the old lease expires, will it remove this information for me in the case of the device falling off line, and how can I accelerate that process so that I can reassign the printer tag to a new IP

Clean up dynamic names

Hello Bind and DHCP users, Sorry for the post to both lists, but it is a dynamic DNS question and I'm not sure where the answer will come from. We replaced the network card in a printer, which had been working, we had a DHCP lease, we had created from DHCP a dynamic DNS forward and reverse

RE: Clean up dynamic names

Honestly, this is like asking for a closet that automatically throws out the items you pitch into it, once the items are deemed obsolete or junk. The DNS database is a repository of information, like a closet, but it has no inherent way of knowing the value or currency of the information that

Re: My Reverse Look Up suddenly stopped working for most servers

On Wed, Feb 8, 2017 at 10:51 AM, Reindl Harald wrote: > frankly - one last time, otherwise don't expect any future answers - if > you get a response on the mailing list then sned your answer to the mailing > list and *not* to the individual which responded > > Am

Re: My Reverse Look Up suddenly stopped working for most servers

I copied and pasted the solution from Outlook email, but I don't see it, so I guess I'll type it. Again, DONE, and I share the solution below from our DNS Admin for the knowledge library; thanks again. PTR records for the specified server below were missing. On Wed, Feb 8, 2017 at 10:51 AM,

Re: Clean up dynamic names

On Wed, Feb 8, 2017 at 1:09 PM, Cuttler, Brian R (HEALTH) < brian.cutt...@health.ny.gov> wrote: > Kevin, > > I understand. Let me refocus the question. > > DHCP: > I know DHCP will remove the info when the old lease expires, will it > remove this information for me in the case of the device

RE: Clean up dynamic names

Bob, Thank you, the assurance that I'd understood the defaults and that nsupdate was the correct tool was all that was missing. I executed the update commands and they worked like a charm. Thank you, Brian === The forward table looks like this hr16038                 A       

RHEL, Centos, Fedora rpm 9.11.0-P3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 http://www.five-ten-sg.com/mapper/bind contains links to the source rpms, and build instructions. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEAREKAAYFAlibpa8ACgkQL6j7milTFsFi5gCfSEhAyxLOEgFDY8aoSkuLnXvD

Re: Bind Queries log file format

> On Feb 7, 2017, at 11:07 PM, Mark Andrews wrote: > > > No, we have a field that has more information in it. Same field E -> > E(version) > > 08-Feb-2017 15:15:44.532 client @0x7fc1c803c600 127.0.0.1#57982/key external > (rock.dv.isc.org): view external: query:

domain-unable-resolve

Helo, Time to time we are having problem in resolving some domains, one of them is "abudawood.com" we unable to resolve through our DNS servers of "ns10.cyberia.net.sa" where I have latest bind version and all, what could be the issue and what is the best way to trouble shoot. My