Displaying 5 results from an estimated 5 matches for "dns_serve".
Did you mean:
dns_server
2009 Jun 08
2
[PATCH] few minor bugfixes
- perform dns lookup on hostname,
- randomize local tunnel port
- bump rpm spec version
updated to include danpb's feedback regarding getaddrinfo
---
main.c | 36 ++++++++++++++++++------------------
ovirt-viewer.spec | 9 ++++++++-
tunnel.c | 29 ++++++++++++++++++++---------
3 files changed, 46 insertions(+), 28 deletions(-)
diff --git a/main.c b/main.c
index
2009 Jun 01
2
[PATCH viewer] few minor bugfixes
- perform dns lookup on hostname,
- randomize local tunnel port
- simple autobuild script
- bump rpm spec version
---
autobuild.sh | 41 +++++++++++++++++++++++++++++++++++++++++
main.c | 14 +++++---------
ovirt-viewer.spec | 9 ++++++++-
tunnel.c | 29 ++++++++++++++++++++---------
4 files changed, 74 insertions(+), 19 deletions(-)
create mode 100755
2015 Mar 10
2
net ads join fails
...ines), they need to be very
> close together.
>
> Rowland
>
Time seems okay, the system is getting it from the first DC, but I found
something interesting in the serverlog:
Not authoritative for '_kerberos.dilken.eu', forwarding
[2015/03/10 22:31:34.148561, 2]
../source4/dns_server/dns_query.c:629(dns_serve
r_process_query_send)
Seems that net ads does not correctly set domain name and/or realm. The
DNS-question should be _kerberos.ad.dilken.eu for which the DNS is
authoritative...
Greetings,
Roman
2009 Jun 10
1
[PATCH] add cmd line option for server vnc port
---
internal.h | 3 +++
main.c | 3 +++
tunnel.c | 7 ++-----
3 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/internal.h b/internal.h
index 80e675e..bd65922 100644
--- a/internal.h
+++ b/internal.h
@@ -71,6 +71,9 @@ extern gboolean check_cert;
/* server we're connecting to */
extern const char* hostname;
+/* port which to connect to the server via vnc */
2015 Mar 10
2
net ads join fails
Oh, I have a pair of samba-4.1.17-DC's, raspberry-pi and dc2 to which make the domain ad.dilken.eu on site Neuoetting.
resolv.conf points to the two dc's:
search ad.dilken.eu
nameserver 192.168.2.33
nameserver 192.168.2.2
In the output I find some relations to dc2 resp. 192.168.2.2, but perhaps it doesn't work as expected..
Greetings
Am 10.03.2015 um 21:23 schrieb Rowland Penny: