starred/nsupdate.info-nsupdate-info

Fork 0

mirror of https://github.com/nsupdate-info/nsupdate.info.git synced 2026-04-26 09:05:54 +03:00

[GH-ISSUE #73] option to test without actual dns server backend #70

New issue

Closed

opened 2026-02-26 09:35:21 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 09:35:21 +03:00

Owner

Originally created by @NotANormalNerd on GitHub (Nov 2, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/73

Originally created by @NotANormalNerd on GitHub (Nov 2, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/73

kerem closed this issue

2026-02-26 09:35:21 +03:00

kerem commented

2026-02-26 09:35:22 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 2, 2013):

it either needs a mock backend or we could use the real backend with some separate dynamically updateable dns zone just for testing.

@ThomasWaldmann commented on GitHub (Nov 2, 2013): it either needs a mock backend or we could use the real backend with some separate dynamically updateable dns zone just for testing.

kerem commented

2026-02-26 09:35:22 +03:00

Author

Owner

@NotANormalNerd commented on GitHub (Nov 3, 2013):

I was thinking of a fake backend...
Could not figure out all interfaces by now

@NotANormalNerd commented on GitHub (Nov 3, 2013): I was thinking of a fake backend... Could not figure out all interfaces by now

kerem commented

2026-02-26 09:35:22 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 10, 2013):

i included a key so everyone can update test.nsupdate.info using that key (but no other host in that zone). the tests only update this single host, so they work now for everybody.

close issue?

@ThomasWaldmann commented on GitHub (Nov 10, 2013): i included a key so everyone can update test.nsupdate.info using that key (but no other host in that zone). the tests only update this single host, so they work now for everybody. close issue?

kerem commented

2026-02-26 09:35:23 +03:00

Author

Owner

@NotANormalNerd commented on GitHub (Nov 20, 2013):

I will test this and get back to this issue.

edit: can you give a reference? Where ist the key?

@NotANormalNerd commented on GitHub (Nov 20, 2013): I will test this and get back to this issue. edit: can you give a reference? Where ist the key?

kerem commented

2026-02-26 09:35:23 +03:00

Author

Owner

@NotANormalNerd commented on GitHub (Nov 21, 2013):

Can you please provide a sample config for the test.nsupdate.info

@NotANormalNerd commented on GitHub (Nov 21, 2013): Can you please provide a sample config for the test.nsupdate.info

kerem commented

2026-02-26 09:35:23 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 22, 2013):

See docs/examples/bind9/named.conf in the repo.

If course the key shown there for nsupdate.info. is not the key used in production for the normal zone updates.

But I used the same secret and put it into a key called "test.nsupdate.info." which may only update the test host.

To enable this, I added this to the configuration:

key "test.nsupdate.info." {
    algorithm hmac-sha512;
    secret "YWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYQ==";
};

And a bit below:

        grant test.nsupdate.info. name test.nsupdate.info;

But please note: you don't need to do anything like this to run the tests, they'll just use the test host provided on our server and they have the correct shared secret for that single host.

@ThomasWaldmann commented on GitHub (Nov 22, 2013): See docs/examples/bind9/named.conf in the repo. If course the key shown there for nsupdate.info. is not the key used in production for the normal zone updates. But I used the same secret and put it into a key called "test.nsupdate.info." which may only update the test host. To enable this, I added this to the configuration: ``` key "test.nsupdate.info." { algorithm hmac-sha512; secret "YWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYQ=="; }; ``` And a bit below: ``` grant test.nsupdate.info. name test.nsupdate.info; ``` But please note: you don't need to do anything like this to run the tests, they'll just use the test host provided on our server and they have the correct shared secret for that single host.

kerem commented

2026-02-26 09:35:23 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Dec 25, 2013):

note: i changed the tests to use a whole test zone, with random host names (so multiple tests can run in parallel).

@ThomasWaldmann commented on GitHub (Dec 25, 2013): note: i changed the tests to use a whole test zone, with random host names (so multiple tests can run in parallel).

kerem commented

2026-02-26 09:35:23 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Nov 7, 2014):

as the tests and travis are working quite reliably now, I don't think we need to implement this mocking stuff.

@ThomasWaldmann commented on GitHub (Nov 7, 2014): as the tests and travis are working quite reliably now, I don't think we need to implement this mocking stuff.