Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Properly implement notifies #56

Closed
miekg opened this issue Mar 28, 2016 · 3 comments
Closed

Properly implement notifies #56

miekg opened this issue Mar 28, 2016 · 3 comments

Comments

@miekg
Copy link
Member

miekg commented Mar 28, 2016

First: the simple: notify on start up.
This was referenced Mar 28, 2016
Closed
Closed
@miekg
Copy link
Member Author

miekg commented Mar 30, 2016

Interesting question; if you want to notify the nameserver in the NSset, how do you resolve those names, if you do not have a resolver to aid. Ask the system? What if the system will ask you?

@miekg
Copy link
Member Author

miekg commented Apr 3, 2016

question answered: use ip address.

Extend this bug to properly implement notifies and primary/secondary communication.

@miekg miekg changed the title outgoing axfr should also implement notifies Properly implement notifies Apr 3, 2016
@miekg
Copy link
Member Author

miekg commented Apr 6, 2016

This has been done.

@miekg miekg closed this as completed Apr 6, 2016
@miekg miekg mentioned this issue Nov 9, 2020
Closed
sgreene570 pushed a commit to sgreene570/coredns that referenced this issue May 17, 2021
@openshift-merge-robot
Merge pull request coredns#56 from sgreene570/bump-for-kube-1.21
842f354 
Bug 1947478: Upstream cherry-picks and downstream dep bumps for kube 1.21 compatability
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@miekg