Visit Our UNIX and Linux User Community

Special Forums Windows & DOS: Issues & Discussions Home Questions Tags Users Unanswered Windows 2016 DNS server returns SERVFAIL for non-existing doma Post 303043616 by vbe on Sunday 2nd of February 2020 06:59:21 AM
Old 02-02-2020
Hi,
Here you nail pin the problem of big structures, the lack of communication between the different responsibilities:
We Unix people never get clear answers from security team or network team, it is you that have to show the others the issue, and its cause before they take into account, mainly because in the case of DNS and proxies e.g they see no problems with Window servers when you are trying something on your lan that is not working as expected it becomes a nightmare having to test things that are not in your hands like the network it goes with trying a similar config on 2 other servers, if it works there, try to figure out what can be the culprit... In other words you have to suggest ( because never a good idea to blame the others for not doing their work seriously...) by showing the case that works and the one that doesnt that it may be a misconfiguration of a port in a switch as you have already changed the cabling with new and not more success... or are you filtered? etc...
I suggest you look with the Windows server team to see if they also have the same issue, and work together to try to explain at the Network team the issue
 
Test Your Knowledge in Computers #613
Difficulty: Medium
Examples of complex numbers in Python are (-5+4j) and (2.3 - 4.6j).
True or False?

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ftp server on old home computer - a few questions

Hi! Very new to unix stuff, and this is my first post to the forum. I'm pretty sure I know enough to know I know nothing, so please be patient with me and don't laugh too hard. Ok, I've got an old computer and a laptop - the old computer was bought in the mid 90's it's still running windows... (1 Reply)
Discussion started by: boredbody
1 Replies

2. Windows & DOS: Issues & Discussions

Install Windows 2003 R2 on existing Windows 2008

Hi, I am trying to install WIndows 2003 R2 Server on existing Windows 2008 server. When I run the 2003 cd it says no disk found. What can be the problem. (2 Replies)
Discussion started by: gunnervarma
2 Replies

3. UNIX for Dummies Questions & Answers

dlsym() returns 0 for an existing function

Sometimes I observe this in gdb: (gdb) br my_function Breakpoint .. at 0x...: file ..., line ... i.e., "my_function" does exist in the current executable. however, dlsym does not find it: (gdb) p dlsym(0,"my_function") $6 = 0 This is a C program; dlsym does find other defined functions and... (2 Replies)
Discussion started by: sds
2 Replies

4. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

5. UNIX for Advanced & Expert Users

Yahoo Interview unanswered questions

Hi guys, please help me get the answers of these questions which I faced in an interview @ Yahoo 1. I want to " ls " few million files, certainly I cannot do so because ls has some restriction in KBs, how can I do it alternatively. 2. Change the system in such a way that while booting up,... (2 Replies)
Discussion started by: gauravsharma29
2 Replies

6. IP Networking

DNS: Dig returns different responses...

Hey everyone, Okay, so I've been having some fun with the dig command, and wanted to dig my old school. Two questions came up from this. So I: dig @8.8.8.8 +recurse njcu.edu ANY and the result is about 8 records, including the SOA record. One of them is this weird TXT record, and the other is... (1 Reply)
Discussion started by: Lost in Cyberia
1 Replies

7. Hardware

Stack Overflow Questions Tags Users Badges Unanswered Ask Question Ask for the explanation of types

I have read a document which tells me the following 4 things are done by the RAM embedded on disk driver controller. But I don't know what's difference between buffer and cache. Thanks! RAM on disk drive controllers 1 firmware 2 speed matching buffer 3 prefetching buffer 4 cache (1 Reply)
Discussion started by: 915086731
1 Replies

8. Solaris

Tilde prefix returns invalid home directory.

I am trying to find the home directory of users on a UNIX (Solaris/AIX) box using echo ~usernameThis does return the home directory for all valid users. For some reason this command also outputs home directory which are non-existent for few users who seem not to have logon access to that... (31 Replies)
Discussion started by: thinkster
31 Replies

9. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies
GIT-BISECT(1)							    Git Manual							     GIT-BISECT(1)

NAME
git-bisect - Find by binary search the change that introduced a bug SYNOPSIS
git bisect <subcommand> <options> DESCRIPTION
The command takes various subcommands, and different options depending on the subcommand: git bisect help git bisect start [<bad> [<good>...]] [--] [<paths>...] git bisect bad [<rev>] git bisect good [<rev>...] git bisect skip [(<rev>|<range>)...] git bisect reset [<commit>] git bisect visualize git bisect replay <logfile> git bisect log git bisect run <cmd>... This command uses git rev-list --bisect to help drive the binary search process to find which change introduced a bug, given an old "good" commit object name and a later "bad" commit object name. Getting help Use "git bisect" to get a short usage description, and "git bisect help" or "git bisect -h" to get a long usage description. Basic bisect commands: start, bad, good Using the Linux kernel tree as an example, basic use of the bisect command is as follows: .ft C $ git bisect start $ git bisect bad # Current version is bad $ git bisect good v2.6.13-rc2 # v2.6.13-rc2 was the last version # tested that was good .ft When you have specified at least one bad and one good version, the command bisects the revision tree and outputs something similar to the following: .ft C Bisecting: 675 revisions left to test after this .ft The state in the middle of the set of revisions is then checked out. You would now compile that kernel and boot it. If the booted kernel works correctly, you would then issue the following command: .ft C $ git bisect good # this one is good .ft The output of this command would be something similar to the following: .ft C Bisecting: 337 revisions left to test after this .ft You keep repeating this process, compiling the tree, testing it, and depending on whether it is good or bad issuing the command "git bisect good" or "git bisect bad" to ask for the next bisection. Eventually there will be no more revisions left to bisect, and you will have been left with the first bad kernel revision in "refs/bisect/bad". Bisect reset After a bisect session, to clean up the bisection state and return to the original HEAD, issue the following command: .ft C $ git bisect reset .ft By default, this will return your tree to the commit that was checked out before git bisect start. (A new git bisect start will also do that, as it cleans up the old bisection state.) With an optional argument, you can return to a different commit instead: .ft C $ git bisect reset <commit> .ft For example, git bisect reset HEAD will leave you on the current bisection commit and avoid switching commits at all, while git bisect reset bisect/bad will check out the first bad revision. Bisect visualize To see the currently remaining suspects in gitk, issue the following command during the bisection process: .ft C $ git bisect visualize .ft view may also be used as a synonym for visualize. If the DISPLAY environment variable is not set, git log is used instead. You can also give command line options such as -p and --stat. .ft C $ git bisect view --stat .ft Bisect log and bisect replay After having marked revisions as good or bad, issue the following command to show what has been done so far: .ft C $ git bisect log .ft If you discover that you made a mistake in specifying the status of a revision, you can save the output of this command to a file, edit it to remove the incorrect entries, and then issue the following commands to return to a corrected state: .ft C $ git bisect reset $ git bisect replay that-file .ft Avoiding testing a commit If, in the middle of a bisect session, you know that the next suggested revision is not a good one to test (e.g. the change the commit introduces is known not to work in your environment and you know it does not have anything to do with the bug you are chasing), you may want to find a nearby commit and try that instead. For example: .ft C $ git bisect good/bad # previous round was good or bad. Bisecting: 337 revisions left to test after this $ git bisect visualize # oops, that is uninteresting. $ git reset --hard HEAD~3 # try 3 revisions before what # was suggested .ft Then compile and test the chosen revision, and afterwards mark the revision as good or bad in the usual manner. Bisect skip Instead of choosing by yourself a nearby commit, you can ask git to do it for you by issuing the command: .ft C $ git bisect skip # Current version cannot be tested .ft But git may eventually be unable to tell the first bad commit among a bad commit and one or more skipped commits. You can even skip a range of commits, instead of just one commit, using the "<commit1>..<commit2>" notation. For example: .ft C $ git bisect skip v2.5..v2.6 .ft This tells the bisect process that no commit after v2.5, up to and including v2.6, should be tested. Note that if you also want to skip the first commit of the range you would issue the command: .ft C $ git bisect skip v2.5 v2.5..v2.6 .ft This tells the bisect process that the commits between v2.5 included and v2.6 included should be skipped. Cutting down bisection by giving more parameters to bisect start You can further cut down the number of trials, if you know what part of the tree is involved in the problem you are tracking down, by specifying path parameters when issuing the bisect start command: .ft C $ git bisect start -- arch/i386 include/asm-i386 .ft If you know beforehand more than one good commit, you can narrow the bisect space down by specifying all of the good commits immediately after the bad commit when issuing the bisect start command: .ft C $ git bisect start v2.6.20-rc6 v2.6.20-rc4 v2.6.20-rc1 -- # v2.6.20-rc6 is bad # v2.6.20-rc4 and v2.6.20-rc1 are good .ft Bisect run If you have a script that can tell if the current source code is good or bad, you can bisect by issuing the command: .ft C $ git bisect run my_script arguments .ft Note that the script (my_script in the above example) should exit with code 0 if the current source code is good, and exit with a code between 1 and 127 (inclusive), except 125, if the current source code is bad. Any other exit code will abort the bisect process. It should be noted that a program that terminates via "exit(-1)" leaves $? = 255, (see the exit(3) manual page), as the value is chopped with "& 0377". The special exit code 125 should be used when the current source code cannot be tested. If the script exits with this code, the current revision will be skipped (see git bisect skip above). You may often find that during a bisect session you want to have temporary modifications (e.g. s/#define DEBUG 0/#define DEBUG 1/ in a header file, or "revision that does not have this commit needs this patch applied to work around another problem this bisection is not interested in") applied to the revision being tested. To cope with such a situation, after the inner git bisect finds the next revision to test, the script can apply the patch before compiling, run the real test, and afterwards decide if the revision (possibly with the needed patch) passed the test and then rewind the tree to the pristine state. Finally the script should exit with the status of the real test to let the "git bisect run" command loop determine the eventual outcome of the bisect session. EXAMPLES
o Automatically bisect a broken build between v1.2 and HEAD: .ft C $ git bisect start HEAD v1.2 -- # HEAD is bad, v1.2 is good $ git bisect run make # "make" builds the app .ft o Automatically bisect a test failure between origin and HEAD: .ft C $ git bisect start HEAD origin -- # HEAD is bad, origin is good $ git bisect run make test # "make test" builds and tests .ft o Automatically bisect a broken test suite: .ft C $ cat ~/test.sh #!/bin/sh make || exit 125 # this skips broken builds make test # "make test" runs the test suite $ git bisect start v1.3 v1.1 -- # v1.3 is bad, v1.1 is good $ git bisect run ~/test.sh .ft Here we use a "test.sh" custom script. In this script, if "make" fails, we skip the current commit. It is safer to use a custom script outside the repository to prevent interactions between the bisect, make and test processes and the script. "make test" should "exit 0", if the test suite passes, and "exit 1" otherwise. o Automatically bisect a broken test case: .ft C $ cat ~/test.sh #!/bin/sh make || exit 125 # this skips broken builds ~/check_test_case.sh # does the test case passes ? $ git bisect start HEAD HEAD~10 -- # culprit is among the last 10 $ git bisect run ~/test.sh .ft Here "check_test_case.sh" should "exit 0" if the test case passes, and "exit 1" otherwise. It is safer if both "test.sh" and "check_test_case.sh" scripts are outside the repository to prevent interactions between the bisect, make and test processes and the scripts. o Automatically bisect a broken test suite: .ft C $ git bisect start HEAD HEAD~10 -- # culprit is among the last 10 $ git bisect run sh -c "make || exit 125; ~/check_test_case.sh" .ft Does the same as the previous example, but on a single line. AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]> DOCUMENTATION
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[2]>. SEE ALSO
Fighting regressions with git bisect[3], git-blame(1). GIT
Part of the git(1) suite NOTES
1. torvalds@osdl.org mailto:torvalds@osdl.org 2. git@vger.kernel.org mailto:git@vger.kernel.org 3. Fighting regressions with git bisect file:///usr/share/doc/git-doc/git-bisect-lk2009.html Git 1.7.1 07/05/2010 GIT-BISECT(1)

Featured Tech Videos

All times are GMT -4. The time now is 04:39 AM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy